Visit Home Page

MPC
MPC - Formats
MPC - FAQ
MPC - Preferences
MPC - History

Möötjelitt - MPC - Formats

MPC can read a number of different files that have been created on a Palm handheld. The table below gives a description of the formats that MPC understands and formats that it doesn't. Please send us an email if you for some reason think that MPC should support another format.

MobileDB Implemented since v1.10

Applications: Handmark

Translates the database and export the content as a tab delimited text file. The data is exported in the same order as they are defined in the database.

funSMS Implemented since v1.9

Applications: funSMS

Translates the database and export the content as a tab delimited text file.

Pilot-DB Implemented since v1.8

Applications: Pilot-DB

Translates the database and export the content as a tab delimited text file. The fields are exported in the same order as they are defined.

List Implemented since v1.8

Applications: List

Translates the database and export the content as a tab delimited text file in the following order:

  • Category
  • Field 1
  • Field 2
  • Note
Arrange Implemented since v1.7

Applications: Arrange

MPC can read and translate Arrange files into two different formats: text and OPML. If you use the text format each item from the Arrange outline will represented as one line in the text file (newlines in the Arrange outline are replaced with the character you have defined in the preference dialog).

OPML is a more complex format that allows MPC to save more information from the Arrange outline, this means that the text from an Arrange items is separated into two parts, title and note, plus that the checkbox status is saved for each item. The first line of text is used as the title.

Comments about Arrange outlines: they are saved as one large outline so MPC doesn't allow you to select a certain outline, it will export all outlines from Arranger into a single file.

Comment about using the OPML format: this translator have had only limited testing so it's possible that you will stumble across a bug, if you happen to do that please send us a message with all relevant details. Secondly, the OPML file generated by MPC have only been tested with OmniOutliner, the OPML files should work with other applications also but we have not tested it.

Handstory Implemented since v1.7

Applications: Handstory

MPC can now read DOC files created with Handstory. Please note that Handstory supports several other formats but MPC only understands the DOC format.

FrogWatch Implemented since v1.6

Applications: FrogWatch

The converter will ask if you want to save the output as text, HTML or both. It will then ask for output file(s). There is no other visible interface.

JFile Implemented since v1.5

Applications: JFile

Please note that Möötjelitt has nothing to do with the freeware application FMSync which makes it possible to sync JFile database with Filemaker, for more information about FMSync, please see VersionTracker or the project page at SourceForge.

Note that there several versions of JFile available and they all have different file formats. Bacuse of this MPC only has limited support of versions 3 and 4, while version 5 and later should work without problems. If you're using a version older than 5 we suggest that you upgrade to the latest version. Other programs (not available yet) from Möötjelitt will only support version 5.

If you need to create JFile databases also, please take a look at our shareware program "JFile Companion".

Limitations of implementation: encryption is not supported in the current version, the fields are exported in the order they are defined (it's not possible to reorder them).

This converter will not present you with a visible interface, it will only ask you for a file to save the information to.

TimeCatch Implemented since v1.5

Applications: TimeCatch

This converter will first ask you for a project to export and then it will ask for a file to save the information to.

Timesheet Implemented since v1.5

Applications: Timesheet

The Timesheet converter will not present you with a visible user interface, it will only ask you for a file to save the information to and then save the translated content of the Timesheet file. The information will be in the following order:

  1. Category
  2. Date
  3. Start time
  4. End time
  5. Lunch (minutes)
Beers Implemented since v1.4

Applications: Beers

The Beers converter will not present you with a visible user interface, it will only ask you for a file to save the information to and then save the translated content of the Beers file. The information will be in the following order:

  1. Name
  2. Brewery
  3. Bitterness
  4. Beer Color
  5. Rank
  6. Notes
BloodPressMgr Implemented since v1.4

Applications: BloodPressMgr

The BloodPressMgr converter will not present you with a visible user interface, it will only ask you for a file to save the information to and then save the translated content of the BloodPressMgr file. The information will be in the following order:

  1. Date
  2. Time
  3. Systolic
  4. Diastolic
  5. Heart
  6. Notes
Memo Implemented since v1.0

Applications: Standard Memo application, pedit (all versions), Memo Plus, DateBk3/4/5, etc.

This is the standard memo database that comes with all Palm devices. Several other Palm applications uses the memo database for importing or exporting information.

MPC will open a window that shows the available memos, see screenshot, you can now use drag-and-drop or the "Export Text" command in the "File" menu to export the text. Note that the MemoDB database will not exist unless you have turned off synchronization of memos.

Memo32 Implemented since v1.0

Applications: Used by the pedit versions that can handle notes that are a maximum of 32K in size.

The interface for working with these memos is exactly the same as for ordinary memos.

Hours Implemented since v1.0

Applications: Hours

Hours is a free time tracking application for the Palm. The Hours converter will not present you with a visible user interface, it will only ask you for a file to save the information to and then save the translated content of the Hours file. The information will be in the following order:

  1. Date
  2. Start time
  3. End time
  4. Lunch
  5. Extra
  6. Rate
  7. Category
  8. Description

MPC will use the different date/number formats defined on your system when exporting.

Expense Implemented since v1.1

Applications: Palm Expense

This is the standard Expense application that comes with most Palm handhelds. MPC will not present a visible interface, it will only ask for a file where the information should be saved. The records are saved in a text file with the fields separated by tabs, in this order:

  1. Category
  2. Date
  3. Type
  4. Payment
  5. Currency
  6. Amount
  7. Mileage
  8. Vendor
  9. City
  10. Attendees
  11. Note

Note that MPC might not recognize all currency formats. It will then write the following in the currency field: "Unknown currency, id = XX" where XX is a number. Should you see this, please report to Möötjelitt the number and what the currency should be. Also note that any newlines in the notes field are replaced by some other text string (default is a space but it can be changed in the preferences)

Call History Implemented since v1.2

Applications: Phone application on VisorPhone Springboard Module and Handspring Treo devices

MPC exports the data in this database in the following order:

  1. Date
  2. Time
  3. Duration
  4. Roaming
  5. Call type
  6. Number
  7. Name

MPC will not present a visible interface, it will only ask for a file where the information should be saved.

DOC files Implemented since v1.3

Applications: Various programs are able to create DOC files. Note: this is not the same as Microsoft Word Doc files.

MPC will not present a visible interface, it will only ask for a file where the text should be saved. Note that the conversion can take some time.

Special note about the DOC format: There is no formal standard for how a DOC format really should look like. Various programs create DOC files that might differ slightly from other DOC files ... which means that MPC might not be able to translate certain DOC files. If this should happen to you, please contact Möötjelitt and let us know.

MPC have been tested with a few files downloaded from Memoware and files created by ShadowPlan, pedit and QuickWord.

QuickWord documents Implemented since v1.3

Applications: QuickWord

MPC will not present a visible interface, it will only ask for a file where the text should be saved. Note that the conversion can take some time.

QuickWord if a part of the QuickOffice package (see below). Note that QuickOffice comes with a conduit that allows you sync with Microsoft Office so this translator is normally of limited use.

SmartList To Go Not implemented

Applications: SmartList To Go

DataViz do provide a Software Development Kit (SDK) for developers, unfortunately it's a Windows only SDK. We have asked for information that would enables us to create an translator but DataViz have answered that the database format is not public.

HourzPro Not implemented

Applications: HourzPro

We have twice asked for the database format but haven't received any kind of reply from Zoskware.

QuickOffice Not implemented

Applications: QuickOffice

QuickOffice comes with a Palm conduit so there is no reason in implementing a simple translator.

TinySheet Not implemented

Applications: TinySheet

We have asked for the database format but haven't received any kind of reply.

ThoughtManager Not implemented

Applications: ThoughtManager

We have asked for the database format but haven't received any kind of reply.

Handbase Not implemented

Applications: Handbase

The file format is currently not public.